Intelligent Cash Handling

ABSTRACT

Aspects of the disclosure relate to cash handling devices that provide intelligent monitoring and management of cash cycles. A cash handling device having at least one processor, a communication interface, and memory may receive, from a mobile device, a request to process a pre-staged transaction. Subsequently, the cash handling device may generate and present a graphical identifier based on the mobile device requesting access to the cash handling device. Next, the cash handling device may verify that the mobile device is authorized to perform the pre-staged transaction based on the graphical identifier being scanned by the mobile device and cause a connection to be established between the cash handling device and the mobile device. Thereafter, the cash handling device may identify and process the pre-staged transaction associated with the mobile device. Then, the cash handling device may generate a notification indicating completed processing of the identified pre-staged transaction.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a non-provisional of and claims the benefit ofpriority to U.S. Patent Application Ser. No. 63/123,201, filed Dec. 9,2020, and entitled “INTELLIGENT CASH HANDLING,” which is herebyincorporated by reference in its entirety for all purposes.

BACKGROUND

Aspects of the disclosure relate to cash handling and servicing in acash-centric environment. In particular, one or more aspects of thedisclosure relate to deploying, configuring, and utilizing cash handlingdevices to provide intelligent monitoring and management of cash cycles.

For enterprises such as retail and financial institutions that oftenhandle large quantities of paper cash every day, managing cashinventories has become increasingly difficult. In many instances, it maybe important to provide a way to digitize cash transactions at a pointof presentment such that physical cash may be managed more efficientlyand effectively.

SUMMARY

Aspects of the disclosure provide effective, efficient, scalable, andconvenient technical solutions that address and overcome the technicalproblems associated with optimizing the technical operations of cashhandling devices and various related computer systems. In particular,one or more aspects of the disclosure provide techniques for deploying,configuring, and utilizing cash handling devices to provide intelligentmonitoring and management of cash cycles.

In accordance with one or more embodiments, a cash handling devicehaving at least one processor, a memory, and a communication interfacemay receive, from a mobile device, a request to process a pre-stagedtransaction. Subsequently, the cash handling device may generate andpresent a graphical identifier based on the mobile device requestingaccess to the cash handling device. Next, the cash handling device mayverify that the mobile device is authorized to perform the pre-stagedtransaction based on the graphical identifier being scanned by themobile device. Based on verifying that the mobile device is authorizedto perform the pre-staged transaction, the cash handling device maycause a connection to be established between the cash handling deviceand the mobile device. Thereafter, the cash handling device may identifyand process the pre-staged transaction associated with the mobiledevice. Then, the cash handling device may generate a notificationindicating completed processing of the identified pre-stagedtransaction.

In accordance with one or more additional embodiments, a cash handlingdevice having at least one processor, a communication interface, a smallscreen display, an item accepting and dispensing device, and a memorymay present a graphical identifier on the small screen display.Subsequently, based on the graphical identifier being scanned by amobile device, the cash handling device may capture authenticationinformation. Then, the cash handling device may receive, via thecommunication interface, from the mobile device, a request to process apre-staged transaction. Next, the cash handling device may verify thatthe mobile device is authorized to perform the pre-staged transactionbased on the captured authentication information. After verifying thatthe mobile device is authorized to perform the pre-staged transactionbased on the captured authentication information, the cash handlingdevice may cause a connection to be established between the cashhandling device and the mobile device and may activate the itemaccepting and dispensing device in an open position to accept ordispense cash in accordance with the pre-staged transaction. Thereafter,the cash handling device may receive or dispense cash, via the itemaccepting and dispensing device, in accordance with the pre-stagedtransaction. Then, the cash handling device may present a notificationindicating completed processing of the pre-staged transaction.

In some embodiments, presenting the graphical identifier may includepresenting a quick response (QR) code. In addition, the QR code may beused for a transaction between the mobile device and the cash handlingdevice.

In some embodiments, verifying that the mobile device is authorized toperform the pre-staged transaction based on the captured authenticationinformation may include verification using mobile authentication.

In some embodiments, receiving the request to process the pre-stagedtransaction may include receiving the request from a smartphone,associated with a user, executing an application associated with afinancial institution. In some embodiments, receiving the request toprocess the pre-staged transaction may include receiving the requestfrom a tablet computer, associated with a financial institution,executing an application associated with the financial institution.

In some embodiments, capturing the authentication information based onthe graphical identifier being scanned by the mobile device may includeidentifying a user associated with the pre-staged transaction.

In some embodiments, causing a connection to be established between thecash handling device and the mobile device may include establishing amobile network connection between the cash handling device and themobile device.

In some embodiments, the cash handling device may verify that the mobiledevice is authorized to perform the pre-staged transaction based onadditional authentication mechanisms including one or more of: one-timepassword, proximity-based authentication, or multifactor authentication.

In some embodiments, after activating the item accepting and dispensingdevice in an open position to accept or dispense cash in accordance withthe pre-staged transaction, the cash handling device may present anotification associated with processing of the pre-staged transaction.In addition, the notification may consist of one or two words.

In accordance with one or more additional embodiments, a cash handlingdevice, at a merchant location of a merchant and integrated with apoint-of-sale terminal, having at least one processor, a communicationinterface, a small screen display, an item accepting device, and amemory may present a graphical identifier on the small screen display.Based on the graphical identifier being scanned by the mobile device ofthe merchant, the cash handling device may capture authenticationinformation. Then, the cash handling device may receive, via acommunication interface, from the mobile device of the merchant, arequest to process a pre-staged transaction to deposit cash designatedas payment to the merchant from a transaction at the point-of-saleterminal. Next, the cash handling device may verify that the mobiledevice of the merchant is authorized to perform the pre-stagedtransaction based on the captured authentication information. Afterverifying that the mobile device of the merchant is authorized toperform the pre-staged transaction based on the captured authenticationinformation, the cash handling device may cause a connection to beestablished between the cash handling device and the mobile device ofthe merchant, and activate an item accepting device in an open positionto accept cash for deposit into the cash handling device. Thereafter,the cash handling device may receive cash from the merchant in an amountspecified during the pre-staged transaction. Then, the cash handlingdevice may validate the received cash at the merchant location and inreal-time. Subsequently, the cash handling device may provide real-timerecognition of the received cash to an account of the merchant.

In some embodiments, providing real-time recognition of the receivedcash to the account of the merchant may include providing the merchantwith immediate access to the cash credited to the account of themerchant.

In some embodiments, providing real-time recognition of the receivedcash to the account of the merchant may include recognizing an immediatenon-provisional credit of the amount deposited to an account of themerchant with a financial institution.

In some embodiments, the cash handling device may, in a subsequentwithdrawal transaction, dispense the cash received from the merchant.

In some embodiments, presenting the graphical identifier may includepresenting a quick response (QR) code. In addition, the QR code may beused for a transaction between the mobile device of the merchant and thecash handling device.

In some embodiments, verifying that the mobile device of the merchant isauthorized to perform the pre-staged transaction based on the capturedauthentication information may include verification using mobileauthentication.

In some embodiments, receiving the request to process the pre-stagedtransaction may include receiving the request from a smartphone,associated with the merchant, executing an application associated with afinancial institution.

In some embodiments, capturing the authentication information based onthe graphical identifier being scanned by the mobile device of themerchant may include identifying the merchant associated with thepre-staged transaction.

In some embodiments, the cash handling device may verify that the mobiledevice of the merchant is authorized to perform the pre-stagedtransaction based on additional authentication mechanisms including oneor more of: one-time password, proximity-based authentication, ormultifactor authentication.

In accordance with one or more additional embodiments, a cash handlingdevice having at least one processor, a communication interface, a smallscreen display, an item accepting and dispensing device, and a memorymay receive, via the item accepting and dispensing device, in a deposittransaction, a deposit that includes one or more banknotes.Subsequently, the cash handling device may scan and digitize, via thescanning unit coupled to the item accepting and dispensing device, at apoint of presentment, the one or more banknotes. Next, the cash handlingdevice may validate the one or more banknotes. Then, the cash handlingdevice may process the one or more banknotes to obtain and store, in adatastore, identification information related to each of the one or morebanknotes. Thereafter, the cash handling device may cause a cashhandling device support server to generate, using the identificationinformation related to each of the one or more banknotes, one or morereports that include information indicative of an overall cash positionof an enterprise in real-time. Then, the cash handling device may causethe cash handling device support server to send one or more commands toa user computing device to display the one or more reports.

In some embodiments, causing the cash handling device support server togenerate the one or more reports that include information indicative ofan overall cash position of an enterprise in real-time may includegenerating the one or more reports based on a real-time cash position ofa first cash handling device associated with the enterprise at a firstlocation, and a real-time cash position of one or more additional cashhandling devices associated with the enterprise at one or moreadditional locations.

In some embodiments, processing the one or more banknotes to obtainidentification information related to each of the one or more banknotesmay cause the cash handling device support server to identify, using anartificial intelligence algorithm, one or more cash transportation needsof the cash handling device.

In some embodiments, processing the one or more banknotes to obtainidentification information related to each of the one or more banknotesmay cause the cash handling device support server to generate and sendone or more alerts based on identifying the one or more cashtransportation needs of the cash handling device.

In some embodiments, processing the one or more banknotes to obtainidentification information related to each of the one or more banknotesmay cause the cash handling device support server to identify adenomination for each banknote deposited into or dispensed from the cashhandling device, monitor a quantity of banknotes stored in the cashhandling device for each denomination, and send one or more alerts whenthe quantity of banknotes stored in the cash handling device for adenomination is below a predetermined threshold.

In some embodiments, validating the one or more banknotes may cause thecash handling device to detect if any of the banknotes deposited mayinclude counterfeit currency, and generate and send one or more alertsbased on detecting the counterfeit currency.

In some embodiments, validating the one or more banknotes may includevalidation using one or more of ultraviolet detection, infrareddetection, magnetic detection, image recognition, or text recognition.

In some embodiments, validating the one or more banknotes may includecomparing the one or more banknotes with stored reference data.

In some embodiments, the generated one or more reports that includeinformation indicative of an overall cash position of an enterprise inreal-time further may include a report on trends in cash demand for anenterprise.

In some embodiments, the generated one or more reports that includeinformation indicative of an overall cash position of an enterprise inreal-time further may include an inventory report that identifies anamount of currency and denominations the currency available to bedispensed at every cash handling device associated with the enterprise.

In some embodiments, the cash handling device may cause the cashhandling device support server to dynamically update the generated oneor more reports based on additional data generated during execution ofone or more additional cash transactions at the cash handling device.

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIGS. 1A and 1B depict an illustrative computing environment fordeploying, configuring, and utilizing cash handling devices to provideintelligent monitoring and management of cash cycles in accordance withone or more example embodiments.

FIGS. 2A-2C depict an illustrative event sequence for deploying,configuring, and utilizing cash handling devices to provide intelligentmonitoring and management of cash cycles in accordance with one or moreexample embodiments.

FIGS. 3A-3E depict another illustrative event sequence for deploying,configuring, and utilizing cash handling devices to provide intelligentmonitoring and management of cash cycles in accordance with one or moreexample embodiments.

FIGS. 4A-4D depict another illustrative event sequence for deploying,configuring, and utilizing cash handling devices to provide intelligentmonitoring and management of cash cycles in accordance with one or moreexample embodiments.

FIGS. 5-12 depict illustrative graphical user interfaces associated withdeploying, configuring, and utilizing cash handling devices to provideintelligent monitoring and management of cash cycles in accordance withone or more example embodiments.

FIGS. 13-15 depict illustrative methods for deploying, configuring, andutilizing cash handling devices to provide intelligent monitoring andmanagement of cash cycles in accordance with one or more exampleembodiments.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

It is noted that various connections between elements are discussed inthe following description. It is noted that these connections aregeneral and, unless specified otherwise, may be direct or indirect,wired or wireless, and that the specification is not intended to belimiting in this respect.

Some aspects of the disclosure relate to deploying, configuring, andutilizing cash handling devices to provide intelligent monitoring andmanagement of cash cycles. For illustrative purposes the financialinstrument discussed throughout the below description is cash. However,as those skilled in the art will realize, the aspects described hereinare not limited to just cash (e.g., paper money and coins), but may alsoinclude other forms of liquid assets such as checks, bank notes, andmoney orders.

FIGS. 1A and 1B depict an illustrative computing environment fordeploying, configuring, and utilizing cash handling devices to provideintelligent monitoring and management of cash cycles in accordance withone or more example embodiments. Referring to FIG. 1A, computingenvironment 100 may include one or more computing devices and/or othercomputer systems. For example, computing environment 100 may include acash handling device support server 110, a financial institution server120, an enterprise server 130, a mobile computing device 140, anadministrative computing device 150, a first cash handling device 160,and a second cash handling device 170.

Cash handling device support server 110 may be configured to supportoperations of one or more cash handling devices, such as cash handlingdevice 160 and cash handling device 170. Financial institution server120 may be associated with a financial institution, and financialinstitution server 120 may be configured to provide account management,transaction history, and/or other functions associated with one or morefinancial accounts maintained by the financial institution. Enterpriseserver 130 (e.g., a point-of-sale device in a store or any other devicethat can receive payment from a payment instrument) may be associatedwith a business or enterprise, and enterprise server 130 may beconfigured to receive, transfer, or otherwise interact with fundsassociated with the business or enterprise. Administrative computingdevice 150 may be configured to be used by an administrative user toconfigure, control, and/or otherwise interact with cash handling devicesupport server 110, cash handling device 160, cash handling device 170,and/or one or more other devices and/or systems included in computingenvironment 100.

Cash handling device 160 may be a cash handling device, such as a cashrecycler, an automated teller machine (ATM) or an automated tellerassistant (ATA), and cash handling device 160 may be configured toprovide one or more automated teller functions and/or other functions,as illustrated in greater detail below. Cash handling device 170 alsomay be a cash handling device, such as an automated teller machine (ATM)or an automated teller assistant (ATA), and cash handling device 170 maybe configured to provide one or more automated teller functions and/orother functions, similar to cash handling device 160. Cash handlingdevice 160 and cash handling device 170 may be located at various (e.g.,multiple) sites and locations, such as at a financial center (e.g., inthe lobby of a bank or behind a teller line) or at a merchant location(e.g., as an automated cash drawer). In one aspect, the cash handlingdevices (e.g., cash handling device 160, and cash handling device 170)may be freestanding and portable.

Mobile computing device 140 may be and/or include a handheld mobiledevice (e.g., a smartphone or tablet) that may be linked to and/or usedby a client user (who may, e.g., be a customer of an enterpriseorganization, such as a financial institution) or by servicing personnel(who may, e.g., service a cash handling device). In some examples,mobile computing device 140 may be and/or include an augmented realitydevice (e.g., a head set-style augmented reality device, or a handheldor mobile display device) or the like. In some instances, mobilecomputing device 140 may allow users to pre-stage a transaction as theuser approaches the cash handling device (e.g., cash handling device160, and cash handling device 170). In receiving the pre-transactioninput, the mobile computing device 140 may cause efficiency gains withrespect to cash transactions that otherwise would not be able to beinitiated until a customer is physically located at the cash handlingdevice (e.g., cash handling device 160, and cash handling device 170).

In one or more arrangements, cash handling device support server 110,financial institution server 120, enterprise server 130, mobilecomputing device 140, and administrative computing device 150 may be anytype of computing device capable of receiving a user interface,receiving input via the user interface, and communicating the receivedinput to one or more other computing devices. For example, cash handlingdevice support server 110, financial institution server 120, enterpriseserver 130, mobile computing device 140, and administrative computingdevice 150 may, in some instances, be and/or include server computers,desktop computers, laptop computers, tablet computers, smart phones, orthe like that may include one or more processors, memories,communication interfaces, storage devices, and/or other components. Asnoted above, and as illustrated in greater detail below, any and/or allof cash handling device support server 110, financial institution server120, enterprise server 130, mobile computing device 140, andadministrative computing device 150 may, in some instances, bespecial-purpose computing devices configured to perform specificfunctions.

Computing environment 100 also may include one or more networks, whichmay interconnect one or more of cash handling device support server 110,financial institution server 120, enterprise server 130, mobilecomputing device 140, administrative computing device 150, cash handlingdevice 160, and cash handling device 170. For example, computingenvironment 100 may include network 190, which may include one or morepublic networks, private networks, and/or sub-networks (e.g., local areanetworks (LANs), wide area networks (WANs), or the like).

Referring to FIG. 1B, cash handling device 160 may include one or moreprocessors 161, memory(s) 162, and communication interface(s) 166. Cashhandling device 160 also may include a display 163, one or more itemaccepting device(s) 164, and one or more item dispensing device(s) 165.A data bus may interconnect processor(s) 161, memory(s) 162, display163, item accepting device(s) 164, item dispensing device(s) 165, andcommunication interface(s) 166. In some embodiments, an item acceptingdevice 164 and an item dispensing device 165 may be a single device(e.g., a single opening for accepting and dispensing cash).

Display 163 may be and/or include a device having a small-screen display(e.g., a small or miniature screen displaying basic and simpledirections). Item accepting device(s) 164 may be and/or include one ormore electro-mechanical systems configured to receive currency, checks,cards, and/or other items (e.g., from a user of cash handling device160) and physically organize and/or store the received items in one ormore canisters, cartridges, and/or other storage components of cashhandling device 160. Item dispensing device(s) 165 may be and/or includeone or more electro-mechanical systems configured to physically retrieveone or more items from one or more canisters, cartridges, and/or otherstorage components of cash handling device 160 and dispense and/orotherwise output the retrieved items (e.g., to a user of cash handlingdevice 160). Additionally or alternatively, item dispensing device(s)165 may include one or more printers and/or other components configuredto print and/or otherwise generate one or more receipts and/or otheritems (which may, e.g., be output to a user of cash handling device160).

Communication interface 166 may be and/or include one or more networkinterfaces configured to support communication between cash handlingdevice 160 and one or more networks (e.g., network 190). Memory 162 maybe and/or include one or more memory units that include one or moreprogram modules having instructions that when executed by processor(s)161 cause cash handling device 160 to perform one or more functionsdescribed herein and/or one or more databases that may store and/orotherwise maintain information which may be used by such program modulesand/or processor(s) 161. In some instances, the one or more programmodules and/or databases may be stored by and/or maintained in differentmemory units of cash handling device 160 and/or by different computingdevices that may form and/or otherwise make up cash handling device 160.

In one or more arrangements, memory 162 may be or include a flash drive(e.g., a compact flash drive). The memory 162 may facilitate a compactbuild that minimizes use of physical components and maximizesportability of the cash handling device (e.g., cash handling device160), for example, by reducing the size of its footprint. In one or morearrangements, physical components of cash handling device 160 may bereduced to the minimum required hardware elements.

In one or more arrangements, display 163 may be a small or miniaturescreen integrated with the cash handling device 160 that is compact andnon-intrusive. In some examples, cash handling device 160 may generateand display, on display 163, a graphical identifier (e.g., a QuickResponse (QR) code, barcode, or other scannable code or identifier).Such a graphical identifier may be used to identify a mobile computingdevice 140 (e.g., a smart phone or a tablet) for communicating with thecash handling device 160 (e.g., to drive or trigger a transaction). Auser of a mobile computing device 140 may be prompted to scan thegraphical identifier using the mobile computing device 140 to establisha communication connection with the cash handling device (e.g., cashhandling device 160) and/or support server (e.g., cash handling devicesupport server 110). Thereafter, transactions may be communicated to thecash handling device (e.g., cash handling device 160) via the user'smobile computing device (e.g., mobile computing device 140). In someexamples, the user of the mobile computing device 140 may capture thegraphical identifier using a mobile phone camera, a QR code scanner, abar code scanner, radio frequency identification (RFID) technology, orthe like. In some examples, the graphical identifier may be a dynamic ortrackable QR code that changes on a periodic basis. The dynamic QR codemay track data including a time, location, date and device type used toscan the code, and may be used to identify users who scanned the code.

In some embodiments, display 163 may generate and present a set of userinterface procedures tailored for visually impaired users. In someembodiments, display 163 may be the only display screen on the cashhandling device 160. In some examples, cash handling device 160 mayprovide, on display 163, only basic and simple directions to a user(e.g., “Insert Cash”, “Take Cash”, “Transaction Complete”). In someexamples, cash handling device 160 may utilize 5^(th) generation (5G)communication technology or a different technology (e.g., Wi-Fitechnology) for fast data transmission with the mobile computing device(e.g., mobile computing device 140).

For instance, in one example scenario, a user may enter a financialcenter with a cash need. Subsequently, the user may pre-stage atransaction on a user mobile computing device (e.g., mobile computingdevice 140, via a mobile application). Next, the user of the mobilecomputing device 140 may be prompted to scan a QR code presented on ascreen 163 on cash handling device 160. Then, cash handling device 160may authenticate the mobile computing device 140 and/or the user of themobile computing device 140, and establish a communication session withthe mobile computing device 140. In turn, cash handling device 160 mayreceive or dispense cash or other financial instruments in accordancewith the pre-staged transaction. For example, the user may deposit orwithdraw cash without physical interaction with the cash handling device(e.g., a contactless interaction). In some examples, cash handlingdevice 160 may be configured to dispense the same currency that wasearlier deposited. Thus, the deposited cash may be placed immediatelyback into use and circulation which may, for example, reduce one-timeexpenses and the time required for servicing the cash handling device.Upon completion of a transaction, cash handling device 160 may provide aconfirmation message to the mobile computing device (e.g., mobilecomputing device 140). Thus, a retail or financial institution mayprovide immediate access and use of funds recently deposited using thecash handling device, system, and method described herein.

In one or more arrangements, the cash handling device (e.g., cashhandling device 160, and cash handling device 170) may use artificialintelligence software and/or functionality (e.g., artificialintelligence (AI) code) to manage and monitor cash positions across anenterprise or financial institution and automatically schedule servicing(e.g., cash transportation services) when a need is detected. Variousartificial intelligence algorithms may be used and adapted for thisapplication, such as neural network algorithms, statisticalclassification algorithms, machine learning algorithms, Bayesian networkalgorithms, swarm intelligence algorithms, logic algorithms, and/orcombinations of the foregoing algorithms. For example, the cash handlingdevice (e.g., cash handling device 160, and cash handling device 170)may enable automatic buying and selling of currency. In someembodiments, the cash handling device (e.g., cash handling device 160,and cash handling device 170) may use artificial intelligence techniquesto detect potential wrongdoing (e.g., money laundering, moneycounterfeiting, and/or other fraudulent or problematic activity). Forexample, a counterfeit detection feature of the cash handling device mayinclude ultraviolet (UV), infrared (IR), magnetic (MG), imagerecognition, serial number recognition, text recognition, or otherdetection functions. Additionally or alternatively, the cash handlingdevice (e.g., cash handling device 160, and cash handling device 170)may send alerts or notifications regarding fraudulent or problematicactivity and trigger investigations.

In one or more arrangements, the cash handling devices (e.g., cashhandling device 160, and cash handling device 170) may be implemented atmultiple or all retail or financial centers such that all cashtransactions may be digitized at a point of presentment rather thanbeing an unorganized collection of separate cash operations at separatelocations (e.g., at an ATM and at a financial center). By digitizingeach and every cash note, the cash handling system (e.g., computingenvironment 100) may provide easily accessible, real-time cash flowinformation for all banks, point-of-sale terminals, and/or automatedteller machines. For example, the cash handling system may allow forcentralized automated monitoring of each and every financial centers'cash note position at any point in time. In some examples, a financialcenter may be able to, immediately, at a point of presentment, receive adigital record or report on cash holdings and automatically manage andmonitor cash levels. In some embodiments, the cash handling device(e.g., cash handling device 160, and cash handling device 170) may storeinformation about its contents including denominations of cash, and sendalerts on which denominations have been deposited or need to bereplenished. In some instances, a detection unit of the cash handlingdevice (e.g., cash handling device 160, and cash handling device 170)may recognize, capture, and sort, denominations of bills and may handleall types of notes (e.g., worn and new) in any currency.

In some instances, uniform implementation of cash handling devices(e.g., cash handling device 160, and cash handling device 170) at retailor financial centers may enable automation of a cash supply chain suchthat just-in-time cash solutions may be implemented (e.g., cash orderingmay be based on supply and demand rather than handled on a periodicbasis). Additionally, equipment such as cash vaults, counters, tellerdrawers, and safes may be downsized. In some embodiments, the cashhandling device (e.g., cash handling device 160, and cash handlingdevice 170) may validate and digitize each note and a server (e.g., cashhandling device support server 110) may generate reports on a site'soverall cash position. In some examples, a server (e.g., cash handlingdevice support server 110) may generate reports on daily and seasonalvariations, or trends, in cash demand.

In some instances, the cash handling device (e.g., cash handling device160, and cash handling device 170) may be integrated with a front-endpoint-of-sale (POS) system (e.g., enterprise server 130). In oneexample, in addition to (e.g., before or after) interacting with the POSterminal (e.g., a cash register), a merchant may perform varioustransactions with the integrated cash handling device located at themerchant location. For example, the merchant may use the integrated cashhandling device to withdraw cash, fill the POS terminal, or pay forgoods or services received. Thus, the cash handling device may serve asan automated cash drawer for the merchant.

In some instances, the cash handling devices (e.g., cash handling device160, and cash handling device 170) may also provide marketing, productoffers and/or purchases, payments, location-specific analytics, and/orthe like, to provide additional services and values. For instance, thecash handling system (e.g., computing environment 100) may drivecontinuous usage by linking users (e.g., clients, consumers) toretailers through targeted marketing, such as locations for withdrawingcash or locations for using a coupon (e.g., driving traffic to amerchant location).

In some instances, the cash handling device (e.g., cash handling device160, cash handling device 170) may utilize blockchain technology and/orother secure communications technology to facilitate operations. Forexample, an operator or servicing personnel may be responsible forrestocking the cash handling device (e.g., cash handling device 160,cash handling device 170), rather than a particular financialinstitution. Blockchain technology may be used by the cash handlingdevice (e.g., cash handling device 160, cash handling device 170) toaccelerate transaction speed and/or facilitate other types oftransactions in addition to cash transactions such as cash withdrawalsand deposits. Additionally or alternatively, the cash handling device(e.g., cash handling device 160, cash handling device 170) may useblockchain technology to track transactions, which may in turn enablethe cash handling device (e.g., cash handling device 160, cash handlingdevice 170) to handle a relatively larger amount of transaction volumewhile reducing its physical cash transportation needs.

In some instances, servicing personnel may unlock the cash handlingdevice (e.g., cash handling device 160, and cash handling device 170)using a handheld or mobile device rather than a dual key and combinationlock. In some examples, the cash handling device (e.g., cash handlingdevice 160, and cash handling device 170) may be notified of theservicing personnel's arrival in advance and other additional detailsregarding the servicing transaction in advance, such that upon arrival,the servicing personnel need only scan their mobile device at aninterface on the cash handling device (e.g., cash handling device 160,and cash handling device 170) in order to trigger the servicingtransaction. The time required for servicing the cash handling device(e.g., cash handling device 160, and cash handling device 170) may bereduced and less prone to error.

In one or more arrangements, the cash handling device (e.g., cashhandling device 160, and cash handling device 170) may be a “headless”device without a screen, keypad, or card reader.

FIGS. 2A-2C depict an illustrative event sequence for deploying,configuring, and utilizing cash handling devices to provide intelligentmonitoring and management of cash cycles in accordance with one or moreexample embodiments. For example, the example event sequence depicted inFIGS. 2A-2C illustrates how a cash handling device, such as cashhandling device 160, may be used to enable touchless deposit and/orwithdrawal transactions from various users. Additionally, techniques maybe implemented to perform authentication be over a mobile network ratherthan conventional routing through ATM and/or backend networks.

Referring to FIG. 2A, at step 201, a customer or other individual mayinitiate a pre-staged transaction on a mobile device (e.g., mobilecomputing device 140). In some embodiments, mobile computing device 140may be a customer-driven tool. For example, mobile computing device 140may be any type of personal portable computing device (e.g., a mobilephone, a smartphone, a personal digital assistant (PDA), a personalmedia device, a tablet computer, and/or the like) capable of providingan individual (e.g., a customer of a financial institution) with aninterface for performing a cash transaction with a cash handling device(e.g., cash handling device 160). For example, mobile computing device140 may be a smartphone executing an application (e.g., a mobileapplication) associated with a financial institution for performing oneor more cash transactions with the cash handling device (e.g., cashhandling device 160). Additionally or alternatively, mobile computingdevice 140 may be an associate-driven tool. For example, mobilecomputing device 140 may be a tablet computer, a laptop computer, and/orthe like executing an application for assisting an individual (e.g., acustomer of a financial institution) in performing a cash transactionwith a cash handling device (e.g., cash handling device 160). Forexample, mobile computing device 140 may be one or more computingdevices utilized by an associate of a financial institution to performand/or assist an individual in performing a cash transaction (e.g., adeposit, a withdrawal, and/or the like) with the cash handling device(e.g., cash handling device 160). At step 202, the user of the mobiledevice may confirm the pre-staged transaction details (e.g., whichaccount to transact with, a dollar amount, and/or the like).

In some instances, mobile computing device 140 may display and/orotherwise present one or more graphical user interfaces (e.g., on adisplay screen of the mobile computing device 140). For example, mobilecomputing device 140 may display and/or otherwise present one or moregraphical user interfaces similar to graphical user interfaces 500, 600,and 700, which are illustrated in FIGS. 5, 6, and 7. As seen in FIG. 5,graphical user interface 500 may include text and/or other informationfor initiating a pre-staged transaction at mobile computing device 140,prompting the user of the mobile computing device 140 to select a typeof transaction being requested by the user of the mobile computingdevice 140 (e.g., “Withdrawal,” “Deposit”). As seen in FIG. 6, graphicaluser interface 600 may include text and/or other information forinitiating a pre-staged transaction at mobile computing device 140,prompting the user of the mobile computing device 140 to select a useraccount associated with the transaction being requested by the user ofthe mobile computing device 140 (e.g., “Checking Account,” “SavingsAccount”). As seen in FIG. 7, graphical user interface 700 may includetext and/or other information for initiating a pre-staged transaction atmobile computing device 140, prompting the user of the mobile computingdevice 140 to confirm a cash amount associated with the transactionbeing requested by the user of the mobile computing device 140 (e.g.,“Amount 1,” “Amount 2,” “Amount 3,” “Enter Different Amount”). It willbe appreciated that other and/or different notifications may also beprovided.

In some embodiments, cash handling device 160 may require users toidentify and/or authenticate themselves to the cash handling device 160before the cash handling device will initiate, perform, complete, and/orfacilitate the transaction (e.g., the pre-staged transaction). Forexample, in some embodiments, the cash handling device 160 may beconfigured to authenticate a user based at least partially on a quickresponse (QR) code and/or one or more other credentials. At step 203,cash handling device 160 may present a graphical identifier on a smallscreen display. For example, cash handling device 160 may present aquick response (QR) code used for a secure transaction between themobile device (e.g., mobile computing device 140) and the cash handlingdevice (e.g., cash handling device 160). Such a graphical identifier maybe used to identify the mobile computing device 140 (e.g., a smart phoneor a tablet) for communicating with the cash handling device 160 todrive or trigger the transaction.

At step 204, cash handling device 160 may cause the mobile computingdevice 140 to scan the graphical identifier. For example, cash handlingdevice 160 may cause the mobile computing device (e.g., the mobilecomputing device 140) to display and/or otherwise present one or moreuser interfaces similar to graphical user interface 800, which isillustrated in FIG. 8. As seen in FIG. 8, user interface 800 may includetext and/or other information prompting the user of the mobile computingdevice to use the mobile computing device (e.g., the mobile computingdevice 140) to capture the graphical identifier associated with the cashhandling device (e.g., cash handling device 160). It will be appreciatedthat other and/or different notifications may also be provided.

Referring to FIG. 2B, at step 205, based on the graphical identifierbeing scanned by the mobile computing device 140, cash handling device160 may capture authentication information. In some examples, incapturing the authentication information, cash handling device 160 mayidentify the user associated with the pre-staged transaction (e.g., theuser with authority to decision the transaction) and/or the deviceassociated with the pre-staged transaction.

At step 206, mobile computing device 140 (e.g., a customer's smartphoneor an associate's tablet computer) may send a request to process thepre-staged transaction, and in turn at step 207, cash handling device160 may receive, via the communication interface, the request to processthe pre-staged transaction.

At step 208, cash handling device 160 may authenticate the user of themobile computing device 140. For example, cash handling device 160 mayverify that the mobile device (e.g., mobile computing device 140) isauthorized to perform the pre-staged transaction based on the capturedauthentication information (e.g., at step 205). For instance, cashhandling device 160 may use mobile authentication for verification thatthe mobile device (e.g., mobile computing device 140) is authorized toperform the pre-staged transaction. In some embodiments, cash handlingdevice 160 may verify that the mobile device (e.g., mobile computingdevice 140) is authorized to perform the pre-staged transaction based onadditional authentication mechanisms including one or more of: one-timepassword, proximity-based authentication, or multifactor authentication.Other types of authentication requests may also be used in addition toor instead of those described.

Referring to FIG. 2C, at step 209, after verifying that the mobiledevice (e.g., mobile computing device 140) is authorized to perform thepre-staged transaction based on the captured authentication information,cash handling device 160 may cause a connection (e.g., a mobile networkconnection) to be established between the cash handling device 160 andthe mobile device (e.g., mobile computing device 140). In turn, at step210, cash handling device 160 may activate the item accepting anddispensing device in an open position to accept or dispense cash inaccordance with the pre-staged transaction. In some examples, afteractivating the item accepting and dispensing device in an open positionto accept or dispense cash in accordance with the pre-stagedtransaction, cash handling device 160 may present a notificationassociated with processing of the pre-staged transaction. For example,cash handling device 160 may display and/or otherwise present agraphical user interface similar to graphical user interface 900, whichis illustrated in FIG. 9. As seen in FIG. 9, graphical user interface900 may include basic and simple directions to a user (e.g., “TakeCash”). It will be appreciated that other and/or different notificationsmay also be provided.

At step 211, cash handling device 160 may receive or dispense cash, viathe item accepting and dispensing device, in accordance with thepre-staged transaction. For example, a user of the mobile computingdevice 140 may simply insert or remove cash without touching cashhandling device 150, and the cash handling device 150 handles the restof the steps for processing the cash transaction. At step 212, cashhandling device 160 may present a notification indicating completedprocessing of the pre-staged transaction. For example, cash handlingdevice 160 may display and/or otherwise present a graphical userinterface similar to graphical user interface 1000, which is illustratedin FIG. 10. As seen in FIG. 10, graphical user interface 1000 mayinclude basic and simple directions to a user (e.g., “TransactionComplete”). Additionally or alternatively, cash handling device 150 maycause a user's mobile computing device (e.g., mobile computing device140) to display and/or otherwise present a graphical user interfacesimilar to graphical user interface 1100, which is illustrated in FIG.11. As seen in FIG. 11, graphical user interface 1100 may include textand/or other information indicating completed processing of thepre-staged transaction. It will be appreciated that other and/ordifferent notifications may also be provided. In addition, in someinstances, one or more steps of the example event sequences may berepeated, skipped, and/or combined.

FIGS. 3A-3E depict another illustrative event sequence for deploying,configuring, and utilizing cash handling devices to provide intelligentmonitoring and management of cash cycles in accordance with one or moreexample embodiments. For example, the example event sequence depicted inFIGS. 3A-3E illustrates how a cash handling device, such as cashhandling device 160, may be used to enable touchless deposit and/orwithdrawal transactions in a merchant use case. For instance, cashhandling device 160 located at a merchant location may serve as anautomated cash drawer for the merchant.

Referring to FIG. 3A, at step 301, a merchant may conduct a transaction(e.g., a cash transaction) at a front-end point-of-sale (POS) system(e.g., enterprise server 130) integrated with a cash handling device(e.g., cash handling device 160). For example, the merchant may receivecash designated as payment to the merchant from the transaction at thepoint-of-sale terminal.

Subsequently, at step 302, a merchant may initiate a pre-stagedtransaction on a mobile computing device (e.g., mobile computing device140). For example, mobile computing device 140 may be any type ofpersonal portable computing device (e.g., a mobile phone, a smartphone,a personal digital assistant (PDA), a personal media device, a tabletcomputer, and/or the like) capable of providing a merchant with aninterface for performing a cash transaction with a cash handling device(e.g., cash handling device 160). At step 303, the merchant, via themobile device, may confirm the pre-staged transaction details (e.g.,which account to deposit/withdraw from, an amount of cash fordeposit/withdrawal, and/or the like). For example, mobile computingdevice 140 may display and/or otherwise present one or more graphicaluser interfaces similar to graphical user interfaces 500, 600, and 700,which are illustrated in FIGS. 5, 6, and 7, as described above.

At step 304, cash handling device 160 may present a graphical identifieron a small screen display. For example, cash handling device 160 maypresent a quick response (QR) code used for a secure transaction betweenthe merchant's mobile device (e.g., mobile computing device 140) and thecash handling device (e.g., cash handling device 160).

Referring to FIG. 3B, at step 305, cash handling device 160 may causethe merchant's mobile device (e.g., mobile computing device 140) to scanthe graphical identifier. For example, cash handling device 160 maycause the mobile computing device (e.g., the mobile computing device140) to display and/or otherwise present one or more user interfacessimilar to graphical user interface 800, which is illustrated in FIG. 8,as described above. In turn, at step 306, based on the graphicalidentifier being scanned by the merchant's mobile device (e.g., mobilecomputing device 140), cash handling device 160 may captureauthentication information. For example, in capturing the authenticationinformation, cash handling device 160 may identify the merchantassociated with the pre-staged transaction (e.g., the user withauthority to decision the transaction).

At step 307, the merchant's mobile device (e.g., mobile computing device140) may send a request to process the pre-staged transaction to depositcash designated as payment to the merchant from a transaction at thepoint-of-sale terminal, and in turn at step 308, cash handling device160 may receive, via the communication interface, the request to processthe pre-staged transaction.

Referring to FIG. 3C, at step 309, cash handling device 160 mayauthenticate the user of the mobile computing device 140. For example,cash handling device 160 may verify that the merchant's mobile device(e.g., mobile computing device 140) is authorized to perform thepre-staged transaction based on the captured authentication information(e.g., at step 306). For example, cash handling device 160 may usemobile authentication for verification that the mobile device (e.g.,mobile computing device 140) is authorized to perform the pre-stagedtransaction. In some embodiments, cash handling device 160 may verifythat the merchant mobile device (e.g., mobile computing device 140) isauthorized to perform the pre-staged transaction based on additionalauthentication mechanisms including one or more of: one-time password,proximity-based authentication, or multifactor authentication. Othertypes of authentication requests may also be used in addition to orinstead of those described.

At step 310, after verifying that the merchant's mobile device (e.g.,mobile computing device 140) is authorized to perform the pre-stagedtransaction based on the captured authentication information, cashhandling device 160 may cause a connection (e.g., a mobile networkconnection) to be established between the cash handling device 160 andthe merchant's mobile device (e.g., mobile computing device 140). Inturn, at step 311, cash handling device 160 may activate the itemaccepting and dispensing device in an open position to accept cash fordeposit into the cash handling device 160 in accordance with thepre-staged transaction. In some examples, after activating the itemaccepting and dispensing device in an open position to accept cash fordeposit into the cash handling device 160, cash handling device 160 maypresent a notification associated with processing of the pre-stagedtransaction. For example, cash handling device 160 may display and/orotherwise present a graphical user interface similar to graphical userinterface 900, which is illustrated in FIG. 9, as described above.

At step 312, cash handling device 160 may receive the cash from themerchant in an amount specified during the pre-staged transaction, viathe item accepting and dispensing device, in accordance with thepre-staged transaction. Referring to FIG. 3D, at step 313, cash handlingdevice 160 may validate, at the merchant location and in real-time, thereceived cash. At step 314, cash handling device 160 may present anotification indicating completed processing of the pre-stagedtransaction. For example, cash handling device 160 may display and/orotherwise present a graphical user interface similar to graphical userinterface 1000, which is illustrated in FIG. 10, as described above.

At step 315, cash handling device 160 may provide real-time recognitionof the received cash to an account of the merchant. For example, cashhandling device 160 may provide the merchant with immediate access tothe cash credited to the account of the merchant. For example, cashhandling device 160 may recognize an immediate non-provisional credit ofthe amount deposited to an account of the merchant with a financialinstitution (e.g., eliminating the need to take the cash back to aprocessing center/financial institution and have it counted before thecredit may be recognized as a non-provisional credit).

At step 316, the merchant's mobile device (e.g., mobile computing device140) may send another request to process a subsequent pre-stagedtransaction (e.g., to withdraw cash from the merchant account). In turn,referring to FIG. 3E, at step 317, cash handling device 160 may receive,via the communication interface, the request to process the subsequentpre-staged transaction. In turn, at step 318, cash handling device 160may activate the item accepting and dispensing device in an openposition to dispense cash from the cash handling device 160 inaccordance with the pre-staged transaction.

At step 319, cash handling device 160 may dispense, via the itemaccepting and dispensing device, in accordance with a cash amountspecified by the merchant in the pre-staged transaction. In someexamples, in the subsequent withdrawal transaction, cash handling device160 may dispense the cash received from the merchant at step 311. Atstep 320, cash handling device 160 may present a notification indicatingcompleted processing of the subsequent pre-staged transaction. Inaddition, in some instances, one or more steps of the example eventsequences may be repeated, skipped, and/or combined.

FIGS. 4A-4D depict another illustrative event sequence for deploying,configuring, and utilizing cash handling devices to provide intelligentmonitoring and management of cash cycles in accordance with one or moreexample embodiments. For example, the example event sequence depicted inFIGS. 4A-4D illustrates how a cash handling device, such as cashhandling device 160, may be used to enable enterprise-wide cash positiondetails and analytics. For instance, techniques may be implemented toenable efficiencies in restocking and transportation, enableimprovements in management of cash inventories and cash positions (e.g.,manage possession of actual physical currency), provide a device-levelunderstanding of an enterprise's cash position, and/or the like.

Referring to FIG. 4A, at step 401, cash handling device 160 may receive,via the item accepting and dispensing device, in a deposit transaction,a deposit comprising one or more banknotes.

At step 402, cash handling device 160 may scan and digitize the one ormore banknotes at a point of presentment. For example, cash handlingdevice 160 may scan and digitize the one or more banknotes via ascanning unit coupled to an item accepting and dispensing device of cashhandling device 160. At step 403, cash handling device 160 may validatethe one or more banknotes. In some examples, in validating the one ormore banknotes, cash handling device 160 may detect if any of thebanknotes deposited include counterfeit currency and, based on detectingthe counterfeit currency, generate and send one or more alerts.Validation of the banknotes may include validation using one or more ofultraviolet detection, infrared detection, magnetic detection, imagerecognition, or text recognition. Such validation may also includecomparing the one or more banknotes with stored reference data (e.g.,predefined templates of authentic banknotes).

At step 404, cash handling device 160 may process the one or morebanknotes. For example, cash handling device 160 may obtainidentification information related to each of the one or more banknotesand store the identification information in a datastore (e.g., at cashhandling device support server 110). In some examples, in processing theone or more banknotes to obtain identification information related toeach of the one or more banknotes, cash handling device 160 may causecash handling device support server 110 to identify a denomination foreach banknote deposited into or dispensed the cash handling device 160,monitor a quantity of banknotes stored in the cash handling device 160for each denomination, and send one or more alerts when the quantity ofbanknotes stored in the cash handling device 160 for a denomination isbelow a predetermined threshold.

Referring to FIG. 4B, in some embodiments, at step 405, cash handlingdevice 160 may cause cash handling device support server 110 to use oneor more artificial intelligence algorithms to monitor cash positionsacross an enterprise. In some examples, cash handling device supportserver 110 may identify one or more cash transportation needs of cashhandling device 160 and automatically schedule servicing (e.g., cashtransportation services). At step 406, cash handling device 160 maycause cash handling device support server 110 to generate one or morealerts (e.g., based on identifying the one or more cash transportationor replenishment needs of one or more cash handling devices). At step407, cash handling device 160 may cause cash handling device supportserver 110 to send the one or more generated alerts. For example, cashhandling device support server 110 may generate and/or send one or morecommands and/or alerts to financial institution server 120 and/oradministrative computing device 140 based on identifying the cashreplenishment needs and/or the cash transportation needs of the cashhandling device to direct and/or cause cash replenishment and/or cashtransportation to be provided to the one or more cash handling devices(e.g., cash handling device 160, cash handling device 170). Additionallyor alternatively, cash handling device support server 110 may generateand/or send one or more commands and/or alerts to one or more operatordevices associated with the one or more cash handling devices (e.g.,cash handling device 160, cash handling device 170), such as one or morecomputing devices associated with one or more store owners or otherresponsible parties for the one or more cash handling devices (e.g.,cash handling device 160, cash handling device 170). Additionally oralternatively, cash handling device support server 110 may generateand/or send one or more commands and/or alerts to one or more cashtransportation entities requesting and/or directing that the one or morecash handling devices (e.g., cash handling device 150, cash handlingdevice 160) be serviced.

At step 408, cash handling device 160 may cause cash handling devicesupport server 110 to generate one or more reports (e.g., using theidentification information related to each of the one or morebanknotes). For example, cash handling device support server 110 maygenerate one or more reports including information indicative of anoverall cash position of an enterprise in real-time. In some examples,the one or more reports may include a report on trends in cash demandfor an enterprise. In some examples, the one or more reports may includean inventory report that identifies an amount of currency anddenominations the currency available to be dispensed at every cashhandling device associated with the enterprise. For example, cashhandling device 150 may display and/or otherwise present a graphicaluser interface similar to graphical user interface 1200, which isillustrated in FIG. 12. As seen in FIG. 12, graphical user interface1200 may include text and/or other information providing a user of acomputing device (e.g., administrative computing device 150) a dashboardof reports including reports that identify real-time cash positions ofan enterprise, trends in cash demand, cash inventory, and/or the like.It will be appreciated that other and/or different notifications orreports may also be provided.

Referring to FIG. 4C, at step 409, cash handling device support server110 may send the one or more generated reports. For example, cashhandling device support server 110 may generate the one or more reportsbased on a real-time cash position of a first cash handling deviceassociated with the enterprise at a first location, and a real-time cashposition of one or more additional cash handling devices associated withthe enterprise at one or more additional locations. At step 410, cashhandling device 160 may cause cash handling device support server 110 tosend one or more commands to a user computing device (e.g.,administrative computing device 150) to display the one or more reports(e.g., on a user interface).

Referring to FIGS. 4C-4D, at steps 411-414, cash handling device 160 mayrepeat steps 401-404 (e.g., in FIG. 4A) for performing one or moreadditional cash transactions. Referring to FIG. 4D, at step 415, cashhandling device 160 may cause cash handling device support server 110 togenerate one or more updated reports (e.g., dynamically updating thegenerated one or more reports based on additional data generated duringexecution of the one or more additional cash transactions). For example,cash handling device support server may generate one or more updatedreports including information indicative of an overall cash position ofan enterprise in real-time. In some examples, the one or more reportsmay include an updated report on trends in cash demand for anenterprise. In some examples, the one or more updated reports mayinclude an inventory report that identifies an amount of currency anddenominations the currency available to be dispensed at every cashhandling device associated with the enterprise. At step 416, cashhandling device support server 110 may send the one or more generatedupdated reports (e.g., for display on a user interface).

FIG. 13 depicts an illustrative method for deploying, configuring, andutilizing cash handling devices to provide intelligent monitoring andmanagement of cash cycles in accordance with one or more exampleembodiments. Referring to FIG. 13, at step 1305, a cash handling devicehaving at least one processor, a communication interface, a small screendisplay, an item accepting and dispensing device, and memory may presenta graphical identifier on the small screen display. At step 1310, basedon the graphical identifier being scanned by a mobile device, the cashhandling device may capture authentication information. At step 1315,the cash handling device may receive, via the communication interface,from the mobile device, a request to process a pre-staged transaction.At step 1320, the cash handling device may verify that the mobile deviceis authorized to perform the pre-staged transaction based on thecaptured authentication information. After verifying that the mobiledevice is authorized to perform the pre-staged transaction based on thecaptured authentication information, the cash handling device may, atstep 1325, cause a connection to be established between the cashhandling device and the mobile device, and at step 1330, activate theitem accepting and dispensing device in an open position to accept ordispense cash in accordance with the pre-staged transaction. At step1335, the cash handling device may receive or dispense cash, via theitem accepting and dispensing device, in accordance with the pre-stagedtransaction. At step 1340, the cash handling device may present anotification indicating completed processing of the pre-stagedtransaction.

FIG. 14 depicts an illustrative method for deploying, configuring, andutilizing cash handling devices to provide intelligent monitoring andmanagement of cash cycles in accordance with one or more exampleembodiments. Referring to FIG. 14, at step 1405, a cash handling devicehaving at least one processor, a communication interface, a small screendisplay, an item accepting and dispensing device, and memory may presenta graphical identifier on the small screen display. At step 1410, basedon the graphical identifier being scanned by a mobile device of amerchant, the cash handling device may capture authenticationinformation. At step 1415, the cash handling device may receive, via acommunication interface, from the mobile device of the merchant, arequest to process a pre-staged transaction to deposit cash designatedas payment to the merchant from a transaction at the point-of-saleterminal. At step 1420, the cash handling device may verify that themobile device of the merchant is authorized to perform the pre-stagedtransaction based on the captured authentication information. Afterverifying that the mobile device of the merchant is authorized toperform the pre-staged transaction based on the captured authenticationinformation, the cash handling device may, at step 1425, cause aconnection to be established between the cash handling device and themobile device of the merchant, and at step 1430, activate the itemaccepting device in an open position to accept cash for deposit into thecash handling device. At step 1435, the cash handling device may receivecash from the merchant in an amount specified during the pre-stagedtransaction. At step 1440, the cash handling device may validate, at themerchant location and in real-time, the received cash. At step 1445, thecash handling device may provide real-time recognition of the receivedcash to an account of the merchant.

FIG. 15 depicts an illustrative method for deploying, configuring, andutilizing cash handling devices to provide intelligent monitoring andmanagement of cash cycles in accordance with one or more exampleembodiments. Referring to FIG. 15, at step 1505, a cash handling devicehaving at least one processor, a communication interface, a small screendisplay, an item accepting and dispensing device, and memory mayreceive, via the item accepting and dispensing device, a deposit thatincludes one or more banknotes. At step 1510, the cash handling devicemay scan and digitize, via a scanning unit coupled to the item acceptingand dispensing device, the one or more banknotes at a point ofpresentment. At step 1515, the cash handling device may process the oneor more banknotes to obtain and store, in a datastore, identificationinformation related to each of the one or more banknotes. At step 1520,the cash handling device may validate the one or more banknotes. At step1525, the cash handling device may cause a cash handling device supportserver to generate, using the identification information related to eachof the one or more banknotes, one or more reports that includeinformation indicative of an overall cash position of an enterprise inreal-time. At step 1530, the cash handling device may cause the cashhandling device support server to send one or more commands to a usercomputing device to display the one or more reports.

One or more aspects of the disclosure may be embodied in computer-usabledata or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices to performthe operations described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the likethat perform particular tasks or implement particular abstract datatypes when executed by one or more processors in a computer or otherdata processing device. The computer-executable instructions may bestored as computer-readable instructions on a computer-readable mediumsuch as a hard disk, optical disk, removable storage media, solid-statememory, RAM, and the like. The functionality of the program modules maybe combined or distributed as desired in various embodiments. Inaddition, the functionality may be embodied in whole or in part infirmware or hardware equivalents, such as integrated circuits,application-specific integrated circuits (ASICs), field programmablegate arrays (FPGA), and the like. Particular data structures may be usedto more effectively implement one or more aspects of the disclosure, andsuch data structures are contemplated to be within the scope of computerexecutable instructions and computer-usable data described herein.

Various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination. Inaddition, various signals representing data or events as describedherein may be transferred between a source and a destination in the formof light or electromagnetic waves traveling through signal-conductingmedia such as metal wires, optical fibers, or wireless transmissionmedia (e.g., air or space). In general, the one or morecomputer-readable media may be and/or include one or more non-transitorycomputer-readable media.

As described herein, the various methods and acts may be operativeacross one or more computing servers and one or more networks. Thefunctionality may be distributed in any manner, or may be located in asingle computing device (e.g., a server, a client computer, and thelike). For example, in alternative embodiments, one or more of thecomputing platforms discussed above may be combined into a singlecomputing platform, and the various functions of each computing platformmay be performed by the single computing platform. In such arrangements,any and/or all of the above-discussed communications between computingplatforms may correspond to data being accessed, moved, modified,updated, and/or otherwise used by the single computing platform.Additionally or alternatively, one or more of the computing platformsdiscussed above may be implemented in one or more virtual machines thatare provided by one or more physical computing devices. In sucharrangements, the various functions of each computing platform may beperformed by the one or more virtual machines, and any and/or all of theabove-discussed communications between computing platforms maycorrespond to data being accessed, moved, modified, updated, and/orotherwise used by the one or more virtual machines.

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one or more of the steps depicted in theillustrative figures may be performed in other than the recited order,and one or more depicted steps may be optional in accordance withaspects of the disclosure.

What is claimed is:
 1. A system comprising: a point-of-sale (POS)terminal at a merchant location of a merchant; a mobile device of amerchant; and a cash handling device, at the merchant location of themerchant, integrated with the point-of-sale terminal and configured tocommunicate with the point-of-sale terminal, wherein the cash handlingdevice comprises a memory storing computer-readable instructions that,when executed by at least one processor of the cash handling device,cause the cash handling device to: present, on a small screen display, agraphical identifier; based on the graphical identifier being scanned bythe mobile device of the merchant, capture authentication information;receive, via a communication interface, from the mobile device of themerchant, a request to process a pre-staged transaction to deposit cashdesignated as payment to the merchant from a transaction at thepoint-of-sale terminal; verify that the mobile device of the merchant isauthorized to perform the pre-staged transaction based on the capturedauthentication information; after verifying that the mobile device ofthe merchant is authorized to perform the pre-staged transaction basedon the captured authentication information, cause a connection to beestablished between the cash handling device and the mobile device ofthe merchant, and activate an item accepting device in an open positionto accept cash for deposit into the cash handling device; receive cashfrom the merchant in an amount specified during the pre-stagedtransaction; validate, at the merchant location and in real-time, thereceived cash; and provide real-time recognition of the received cash toan account of the merchant.
 2. The system of claim 1, wherein providingreal-time recognition of the received cash to the account of themerchant comprises providing the merchant with immediate access to thecash credited to the account of the merchant.
 3. The system of claim 1,wherein providing real-time recognition of the received cash to theaccount of the merchant comprises recognizing an immediatenon-provisional credit of the amount deposited to an account of themerchant with a financial institution.
 4. The system of claim 1, whereinthe cash handling device comprises a memory storing additionalcomputer-readable instructions that, when executed by the at least oneprocessor of the cash handling device, cause the cash handling deviceto: in a subsequent withdrawal transaction, dispense the cash receivedfrom the merchant.
 5. The system of claim 1, wherein presenting thegraphical identifier comprises presenting a quick response (QR) code,wherein the QR code is used for a transaction between the mobile deviceof the merchant and the cash handling device.
 6. The system of claim 1,wherein verifying that the mobile device of the merchant is authorizedto perform the pre-staged transaction based on the capturedauthentication information comprises verification using mobileauthentication.
 7. The system of claim 1, wherein receiving the requestto process the pre-staged transaction comprises receiving the requestfrom a smartphone, associated with the merchant, executing anapplication associated with a financial institution.
 8. The system ofclaim 1, wherein capturing the authentication information based on thegraphical identifier being scanned by the mobile device of the merchantcomprises identifying the merchant associated with the pre-stagedtransaction.
 9. The system of claim 1, wherein the cash handling devicecomprises a memory storing additional computer-readable instructionsthat, when executed by the at least one processor of the cash handlingdevice, cause the cash handling device to: verify that the mobile deviceof the merchant is authorized to perform the pre-staged transactionbased on additional authentication mechanisms including one or more of:one-time password, proximity-based authentication, or multifactorauthentication.
 10. A method comprising: at a cash handling device, at amerchant location of a merchant and integrated with a point-of-saleterminal, comprising at least one processor, a communication interface,a small screen display, an item accepting device, and memory:presenting, by the at least one processor, on the small screen display,a graphical identifier; based on the graphical identifier being scannedby a mobile device of a merchant, capturing, by the at least oneprocessor, authentication information; receiving, by the at least oneprocessor, via a communication interface, from the mobile device of themerchant, a request to process a pre-staged transaction to deposit cashdesignated as payment to the merchant from a transaction at thepoint-of-sale terminal; verifying, by the at least one processor, thatthe mobile device of the merchant is authorized to perform thepre-staged transaction based on the captured authentication information;after verifying that the mobile device of the merchant is authorized toperform the pre-staged transaction based on the captured authenticationinformation, causing, by the at least one processor, a connection to beestablished between the cash handling device and the mobile device ofthe merchant, and activating, by the at least one processor, the itemaccepting device in an open position to accept cash for deposit into thecash handling device; receiving, by the at least one processor, cashfrom the merchant in an amount specified during the pre-stagedtransaction; validating, by the at least one processor, at the merchantlocation and in real-time, the received cash; and providing, by the atleast one processor, real-time recognition of the received cash to anaccount of the merchant.
 11. The method of claim 10, wherein providingreal-time recognition of the received cash to the account of themerchant comprises providing the merchant with immediate access to thecash credited to the account of the merchant.
 12. The method of claim10, wherein providing real-time recognition of the received cash to theaccount of the merchant comprises recognizing an immediatenon-provisional credit of the amount deposited to an account of themerchant with a financial institution.
 13. The method of claim 10,further comprising: in a subsequent withdrawal transaction, dispensingthe cash received from the merchant.
 14. The method of claim 10, whereinpresenting the graphical identifier comprises presenting a quickresponse (QR) code, wherein the QR code is used for a transactionbetween the mobile device of the merchant and the cash handling device.15. The method of claim 10, wherein verifying that the mobile device ofthe merchant is authorized to perform the pre-staged transaction basedon the captured authentication information comprises verification usingmobile authentication.
 16. The method of claim 10, wherein receiving therequest to process the pre-staged transaction comprises receiving therequest from a smartphone, associated with the merchant, executing anapplication associated with a financial institution.
 17. The method ofclaim 10, wherein capturing the authentication information based on thegraphical identifier being scanned by the mobile device of the merchantcomprises identifying the merchant associated with the pre-stagedtransaction.
 18. The method of claim 10, further comprising: verifyingthat the mobile device of the merchant is authorized to perform thepre-staged transaction based on additional authentication mechanismsincluding one or more of: one-time password, proximity-basedauthentication, or multifactor authentication.
 19. One or morenon-transitory computer-readable media storing instructions that, whenexecuted by a cash handling device, at a merchant location of a merchantand integrated with a point-of-sale terminal, comprising at least oneprocessor, a communication interface, a small screen display, an itemaccepting device, and memory, cause the cash handling device to:present, on the small screen display, a graphical identifier; based onthe graphical identifier being scanned by a mobile device of a merchant,capture authentication information; receive, via a communicationinterface, from the mobile device of the merchant, a request to processa pre-staged transaction to deposit cash designated as payment to themerchant from a transaction at the point-of-sale terminal; verify thatthe mobile device of the merchant is authorized to perform thepre-staged transaction based on the captured authentication information;after verifying that the mobile device of the merchant is authorized toperform the pre-staged transaction based on the captured authenticationinformation, cause a connection to be established between the cashhandling device and the mobile device of the merchant, and activate theitem accepting device in an open position to accept cash for depositinto the cash handling device; receive cash from the merchant in anamount specified during the pre-staged transaction; validate, at themerchant location and in real-time, the received cash; and providereal-time recognition of the received cash to an account of themerchant.
 20. The one or more non-transitory computer-readable media ofclaim 19, wherein verifying that the mobile device of the merchant isauthorized to perform the pre-staged transaction based on the capturedauthentication information comprises verification using mobileauthentication.